Skip to content

Conversation

@galpeter
Copy link
Contributor

By adding version information to the debugger protocol
it is possible to report if the debugger client and server
have different expectations on debugger workings (opcodes, types, etc.).

@galpeter galpeter added enhancement An improvement feature request Requested feature debugger Related to the debugger labels Jan 16, 2018
/**
* JerryScript debugger protocol version.
*/
#define JERRY_DEBUGGER_VERSION (4)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's start with version 0.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would start with 1 if that's not a problem for you (zero is not really a version number imho).

By adding version information to the debugger protocol
it is possible to report if the debugger client and server
have different expectations on debugger workings (opcodes, types, etc.).

JerryScript-DCO-1.0-Signed-off-by: Peter Gal pgal.u-szeged@partner.samsung.com
@galpeter galpeter force-pushed the debugger-versioning branch from 8db685d to 1e63685 Compare January 18, 2018 11:59
@robertsipka
Copy link
Contributor

LGTM (informally)

Copy link
Contributor

@LaszloLango LaszloLango left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@yichoi
Copy link
Contributor

yichoi commented Jan 23, 2018

LGTM

@yichoi yichoi merged commit 40d05cd into jerryscript-project:master Jan 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

debugger Related to the debugger enhancement An improvement feature request Requested feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants